Split mapping for dynamic rendering and maintaining consistency of data processed by applications

ABSTRACT

The present invention enables a system to efficiently maintain an ancillary pane containing a projection of document content, and content derived therefrom, while the underlying document is being edited. In one embodiment, an acronym pane displays a list of acronyms used in a document and one or more expansions of those acronyms. A data store containing maps is used to index which paragraphs contain which acronyms, and which acronyms are associated with which expansions. As sections of content are added, modified, or deleted, acronyms and expansions are added to and/or removed from the data store, causing the acronym pane to be updated.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. provisional patentapplication No. 62/598,459, entitled “RESUMPTION OF ACTIVITIES USINGACTIVITY DATA COLLECTED BY AN OPERATING SYSTEM”, which was filed on Dec.13, 2017, and which is expressly incorporated herein by reference in itsentirety.

BACKGROUND

Document-based productivity applications, such as word processors,presentation software, spreadsheet applications, web browsers, and thelike typically display document content in an authoring pane. Thisauthoring pane is often centered within the application, consuming amajority of the application's display space. However, document-basedapplications may also provide functionality in ancillary panes, whichmay be displayed adjacent to the main document content. Spellcheckers,style selectors, search boxes, and the like, may be presented inancillary panes, enabling user interaction with the feature withoutoccluding main document content.

Some ancillary panes display content derived from the main documentpane. However, extracting and processing content for display in anancillary pane may be computationally expensive, particularly for largedocuments, and when the underlying content is being added to, updated,and deleted frequently as a user edits the document, efficientlymaintaining the content of the task pane has proved challenging.

In addition, some productivity applications don't display add-in outputrenderings efficiently. For example, a word processor may includeadd-ins for a spell checker. Providing displays of information in theseadd-ins, which can be in an ancillary pane, can be difficult since thecontent in the authoring pane may be incompatible with the contentstored by the add-in and displayed in the ancillary pane.

SUMMARY

This invention addresses the shortcomings of some existing systems byproviding software systems where add-ins manage data received frommultiple sources, and store such data in at least two collections: onecollection for dynamically updating the ancillary pane and the othercollection for maintaining consistency between an authoring pane and theancillary pane. These collections are synchronized as additional changesare received from the sources and as the user interacts with theauthoring pane. The collections enable a more efficient display ofplug-in data.

In one embodiment, an identifier (word, acronym, citation, name, etc.)is extracted from a document. Data related to the identifier(definitions, acronym expansions, citation details, contact information,etc.) is stored in the collections, along with the identifier. These twocollections are maintained in sync as document content is changed. Theseupdates coordinate the authoring pane and the ancillary pane, whichultimately improves user interaction with the computer, reducesinadvertent inputs, enhances user understanding of the document, andincreases user satisfaction with the application. The updates alsoimprove the performance speed in which an application can process,store, and display data.

One technological problem solved by the claimed embodiments is thechallenge of processing large documents quickly. Many algorithmsincrease processing time linearly with an increase in document size.However, the claimed embodiments enable an ancillary pane to be updatedcorrectly and completely as the underlying document changes, but inconstant time. Efficiently updating an acronym pane reserves additionalcomputing resources for other tasks, such as displaying an additionalancillary pane.

Another technological problem solved by the claimed embodiments is thedifficulty in maintaining a separate display of portions of documentcontent while edits are made to the underlying document, particularlywhen the portions of document content have been combined forrepresentation by a single instance, augmented with additionalinformation, or otherwise changed from how they appear in the underlyingdocument. Naïve solutions, such as repeatedly scanning the document,consume significant amounts of processing resources and increaseresponse time to user input.

In one embodiment, an application displays an authoring pane and anadd-in of the application causes a display of an ancillary panedisplaying a list of identifiers and data associated with theidentifiers. The plug-in efficiently updates the ancillary pane as thedocument is edited. The plug-in maintains one data store that has twocollections: one collection for mapping sections of the document to theidentifiers, and another collection for mapping the identifiers to therelated data, e.g., relating words to their definitions.

In one illustrative embodiment, an acronym pane displays a list ofacronyms used in a document and one or more expansions of thoseacronyms. When the document contains multiple instances of an acronym,the acronym pane displays a single representative instance. However,acronyms can have multiple meanings (hereinafter “expansions”), suchthat the same acronym is used to mean different things throughout thedocument. In these scenarios, the acronym may be displayed once in theacronym pane along with the different expansions.

As such, edits to the document may introduce a first instance of anacronym or remove a final instance of an acronym, necessitating anupdate to the acronym pane. However, adding a subsequent instance, orremoving one of many instances, does not add or remove the acronym fromthe acronym pane. Similarly, the system may also track when a firstinstance of an acronym having a particular expansion is added and when alast instance of the acronym having a particular expansion is removed,causing the corresponding expansion to be added or removed from theacronym pane.

For example, if the document contains the text “EDC” in three differentsections, the acronym pane may display “EDC” once, along with anexpansion, e.g. “European Development Center”. However, if one of theinstances is determined to refer to “Error Detection and Correction”,both expansions will be displayed in the acronym pane.

In one embodiment, expansions do not necessarily appear in the document,but are identified by the acronym processing service based on thecontext (e.g. surrounding text, images, formatting) of the acronym. Forexample, the acronym processing service may determine that “EDC” standsfor “Error Detection and Correction”, even if “Error Detection andCorrection” does not appear in the document. In one embodiment, theacronym processing service makes this determination based on a glossaryof terms extracted from a collection of documents related to the userand stored in a remote data store, the remote data store can include anyresource, including word processing documents, emails, calendarappointments, slide decks, and the like. The remote data store can alsoinclude a remote computing device that scans through any type ofdocument, file, or database too extract data such as contactinformation, definitions, citation details, acronym expansions, or otherdata related to an identifier. In addition, expansions may also bedetermined from a dictionary or extracted from files or a document.

While acronyms and expansions are discussed throughout this disclosure,they are but one example of identifiers that may be extracted from adocument, augmented with related data, and kept in sync as the documentis edited. The techniques disclosed herein apply to any type ofidentifier, such as a name, word, acronym, citation, etc., or any othertype of content. In addition, the techniques disclosed herein can applyto any type of data related to the identifier, such as a definition,acronym expansion, citation details, etc. Similarly, sections of contentmay include paragraphs, slide deck text boxes, spreadsheet cells,database rows, or any other source of content. By breaking a largerdocument into sections of content, analysis can be limited to thatsection of content, avoiding re-processing the entire document.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key or essentialfeatures of the claimed subject matter, nor is it intended to be used asan aid in determining the scope of the claimed subject matter. The term“techniques,” for instance, may refer to system(s), method(s),computer-readable instructions, module(s), algorithms, hardware logic,and/or operation(s) as permitted by the context described above andthroughout the document.

BRIEF DESCRIPTION OF THE DRAWINGS

The Detailed Description is described with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Thesame reference numbers in different figures indicates similar oridentical items. References made to individual items of a plurality ofitems can use a reference number with a letter of a sequence of lettersto refer to each individual item. Generic references to the items mayuse the specific reference number without the sequence of letters.

FIG. 1 shows a document-based application including an acronym panedisplaying acronyms that have been extracted from the document.

FIG. 2 shows a document-based application including an acronym panedisplaying acronyms that have been extracted from the document, in whichan existing section has been divided into two sections.

FIG. 3 shows a document-based application including an acronym panedisplaying acronyms that have been extracted from the document in whicha new section has been added and an existing section has been modified.

FIG. 4 shows a document-based application including an acronym panedisplaying acronyms that have been extracted from the document in whicha section has been removed from the document.

FIG. 5 shows a document-based application including an acronym panedisplaying acronyms that have been extracted from the document,including references to where the particular acronym expansion wasidentified.

FIG. 6 shows diagrams of data types returned by an acronym processingservice.

FIG. 7 shows diagrams of data types used to store acronyms, expansions,and the sections of content they are associated with.

FIG. 8 is a flow diagram showing aspects of a routine for updating atask pane displaying acronyms in response to a newly added section ofcontent.

FIG. 9 is a flow diagram showing aspects of a routine for updating atask pane displaying acronyms in response to a deleted section ofcontent.

FIG. 10 is a flow diagram showing aspects of a routine for updating atask pane displaying acronyms based on an updated section of content.

FIG. 11 is a computer architecture diagram illustrating an illustrativecomputer hardware and software architecture for a computing systemcapable of implementing aspects of the techniques and technologiespresented herein.

DETAILED DESCRIPTION

As used herein, “acronym” refers to a series of letters, oftencapitalized, that refer to a series of words that often begin withletters of the acronym. For example, “ECD” is an acronym, as it mayrefer to “European Development Center”, “AI+R” may refer to ArtificialIntelligence and Research, and “NLX” may refer to “Natural LanguageeXperiences”.

As used herein, “expansion” refers to a series of words associated withthe letters of an acronym. For example, “European Development Center” ison expansion for the acronym “EDC”. Acronyms may have multipleexpansions, e.g. “Error Detection and Correction” and “EuropeanDevelopment Center”.

As used herein, “object” refers to an abstraction commonly used incomputer programming to group related pieces of data and methods thatoperate on that data. Objects may be associated with a class type, suchas “ParagraphAcornym”.

As used herein, “section”, as in a “section of content”, refers to asection of a file can be any definitive unit of data, such as a page,side, tab, worksheet, column, row, video segment, audio segment, etc. Inaddition, a section of a file can be defined by text or data having aparticular format, such as an annotation, a header, a footer, afootnote, column header, row header, etc.

FIG. 1 shows a document-based application 100 including an acronym panedisplaying acronyms that have been extracted from the document. In oneembodiment, application 100 executes on computing device 102, andincludes a document-based application including a menu 110, a documentauthoring pane 120, and an acronyms pane 140.

Document authoring pane 120 includes text-based content divided into twosections. The content includes a number of acronyms, including WWW 122,HTML 124, WWW 126, WWW 128, DVD 130, and WWW 132. While there aremultiple instances of the acronym WWW, not all instances are associatedwith the same expansion, as discussed below.

Acronym pane 140 lists three acronyms found in the document: DVD 142,HTML 148, and WWW 152, with arrows associating the acronyms with one ormore instances of the acronyms contained in the document.

Each acronym in pane 140 includes one or more expansions. For example,DVD 142, found in the 2^(nd) section, may be expanded as “Digital VideoDisc” 144 or Digital Versatile Disc” 146. Similarly, HTML 148, locatedin the 1^(st) section, is associated with the expansion “HyperTextMarkup Language” 150. WWW 152 is associated with the expansion “WildWild West” 154, found in the 2^(nd) section, and “World Wide Web” 156,found in the 1^(st) and 2^(nd) sections.

In the case of WWW 152, which expansion is associated with whichparagraph is determined based on contextual data. For example, in the1^(st) section, WWW 122 is discussed in the context of the informationage and the Internet, and so the expansion “World Wide Web” isassociated with it. On the other hand, in the 2^(nd) section, WWW 126 isdiscussed in the context of a 1999 American steam punk western actioncomedy film, and as such is associated with the expansion “Wild WildWest” 154.

FIG. 2 shows a document-based application 200 including an acronym pane140 displaying acronyms 142, 148, and 152 that have been extracted fromthe document, in which an existing section of content has been dividedinto two sections of content. Specifically, the 2^(nd) section ofcontent has been split in two, creating a 3^(rd) section of content andcausing an update to the 2^(nd) section.

Updating a section of content is described below in conjunction withFIG. 9. Briefly, however, in one embodiment, the update to the 2^(nd)section is processed by identifying acronyms included in the 2^(nd)section after the split, and inserting them into the data store asdescribed below in conjunction with FIG. 8. In one embodiment, thecontents of the 2^(nd) section are transmitted to an acronym processingservice, which returns a list of ParagraphAcronym objects, oneParagraphAcronym for each acronym found. Each ParagraphAcronym objectmay include a ParagraphID, the identified Acronym, and a list of one ormore Expansions objects. In one embodiment, before the acronymprocessing service is invoked, the second section is screened forpotential acronyms, omitting a call to the acronym processing service ifno potential acronyms are found.

In one embodiment, each of the returned ParagraphAcronym objects isinserted into the data store as if it were a newly added paragraph.However, some acronyms that were part of the 2^(nd) section may now, asa result of the split, be part of the 3^(rd) section, requiring anupdate to the data store. To accomplish this, in addition to insertingacronyms, each acronym and expansion that is added to the data store, orthat would have been added to the data store if it didn't exist already,is tagged. Then, all untagged expansions and acronyms are removed fromthe data store as described below in conjunction with FIG. 9. In thisway, not only are acronyms that remain in the 2^(nd) section representedas such in the data store, acronyms that have been removed from asection to are no longer represented as such in the data store.

In one embodiment, splitting the 2^(nd) section in two has the effect ofcreating a 3^(rd) section, which is added as discussed below inconjunction with FIG. 8. Briefly, however, in one embodiment, the 3^(rd)section is provided to the acronym processing service, which returns alist of ParagraphAcronym objects, each containing a ParagraphID, a Nameof an identified acronym (e.g. “EDM”), and one or more Expansionsobjects, each of which contains name of the acronym, a description ofthe acronym, a source type (email, file, etc.), a score, and lists ofrelated emails, related files, related people, and related expansions,as discussed above.

Data from each ParagraphAcronym object is inserted into the data store.In one embodiment, the data store iterates through the ParagraphAcronymand checks to see if the acronym exists in a mapping of Acronyms toAcronymExpansions objects, where each AcronymExpansions object includesthe Acronym, an Expansions mapping of expansions to ExpansionWrapperobjects, and a SourceParagraph mapping of ParagraphIDs to lists ofExpansions. Each ExpansionWrapper object includes an Expansion object asdiscussed above and a SourceParagraphs set of ParagraphIDs that theExpansion object is associated with. Specifically, the SourceParagraphsset of ParagraphIDs indicates which paragraphs contain an acronym ofthis ExpansionWrapper object's Expansion.

In one embodiment, if the acronym does not exist in the data store'sAcronyms mapping of Acronyms to AcronymExpansions objects, anAcronymExpansions object is created, and a (Acronym, AcronymExpansionsobject) pair is added to the Acronyms mapping.

Then, the data store iterates through Expansion objects included in theParagraphAcronym. The data store uses the Acronyms mapping to look upthe AcronymExpansions object associated with the returned acronym (e.g.“EDC”), and determines if there is already an entry for this expansion(e.g. “Error Detection and Correction”) in the Expansions mapping ofExpansions to ExpansionWrapper objects. If not, a new ExpansionWrapperobject is created, with a reference to the Expansion object, andinserted into the Expansions mapping. Next, the ParagraphID is added tothe SourceParagraphs mapping of the generated AcronymExpansions object.

However, if the acronym does exist in the data stores' Acronyms mapping,that means this acronym already exists in the document, and a newAcronymExpansions object does not need to be generated. However, nowthat the acronym is associated with a new section of content, theParagraphID is added to the existing AcronymExpansions' SourceParagraphmapping, indicating that this section also includes the acronym.

Similarly, whether an ExpansionWrapper object was created, or if italready existed (indicating that a section of content—possibly adifferent section or possibly the same section—already has an instanceof the identified acronym having the identified expansion), theidentified section is added to the ExpansionWrapper object'sSourceParagraphs set.

Once the data store has been updated, task pane 140 may be updated bytraversing the updated Acronyms mapping of Acronyms to AcronymExpansionobjects. FIG. 2 depicts this change in that acronym expansions 144, 146,and 156 are now associated with the 3^(rd) section instead of the 2^(nd)section, while the expansion “Wild Wild West” 154 is included in the2^(nd) and 3^(rd) sections.

FIG. 3 shows a document-based application 300 including an acronym pane140 displaying acronyms 158, 148, 162, and 152 that have been extractedfrom the document in which a new section has been added and an existingsection has been modified. In this embodiment, a new section has beenadded between the 1^(st) and 2^(nd) section, while the last section, nowthe 4^(th) section, has been modified, replacing the acronym DVD withVHS. In one embodiment, ParagraphIDs are globally unique identifiers(GUIDs), and so adding a section does not affect the order or content ofexisting sections.

In one embodiment, the 2^(nd) section is inserted into the data set asdescribed below in conjunction with FIG. 8, adding another section inwhich the “World Wide Web” expansion of the acronym WWW 152 is located.Also, new acronym CERN 158, with expansion “European Organization forNuclear Research” 160 is added.

The update to what is now the 4^(th) section has the effect of removingthe DVD acronym 142 while adding the acronym VHS 162 and correspondingexpansion “Video Home System” 164.

FIG. 4 shows a document-based application 400 including an acronym pane140 displaying acronyms 158, 148, and 152 that have been extracted fromthe document, where a section has been removed from the document.

In this depiction, the 3^(rd) and 4^(th) sections have been removed,causing some but not all of the instances of the “World Wide Web”expansion 156 of the WWW acronym 152 to be removed. Moreover, allinstances of the “Wild Wild West” expansion 154 of WWW acronym 152 havebeen removed, causing the corresponding entry in the acronym pane 140 tobe removed.

FIG. 5 shows a document-based application 500 including an acronym pane140 displaying acronyms AI+R 518, EDC 514, and NLX 516 that have beenextracted from the document, including references 538, 534, 535, and 536to where the particular acronym expansion was identified.

This embodiment depicts 2 sections, the first including acronyms NLX 502and EDC 504, the second including acronyms NLX 506 and AI+R 508.Acronyms pane 140 depicts the three acronyms 518, 514, and 516. Theseacronyms are depicted in alphabetical order, but other orders aresimilarly contemplated, including the order in which acronyms appear inthe document, an order that prioritizes frequently encountered acronyms,an order that prioritizes acronyms associated with multiple expansions,and the like. In another embodiment, acronym pane 140 may displayacronyms currently visible in document authoring pane 120.

The acronym AI+R 518 is associated with one expansion, “ArtificialIntelligence and Research” 528, which is associated with an indication538 that this expansion was found in the user's email 538. Indication538 includes an arrow that when clicked displays at least a portion ofthe email containing the acronym's expansion.

The acronym EDC 514 is associated with two expansions, “EuropeanDevelopment Center” 524, and “Error Detection and Correction” 525.Expansion 524 is associated with indication 534 that expansion “EuropeanDevelopment Center” 524 was found in the user's email, while expansion525 is associated with indication 535 that “Error Detection andCorrection” 525 was found in one of the user's files. In one embodiment,a user is able to click on indication 534 to view at least a portion ofthe user's email containing expansion 524, while a user is enabled toclick on indication 535 to view at least a portion of the documentcontaining expansion 525.

The acronym NLX 516 is associated with one expansion, “Natural LanguageExperiences” 526, which is associated with an indication 536 that thisexpansion was found in one of the user's files. Clicking on indication536 may similarly display at least a portion of the file expansion 526was found in.

FIG. 6 shows diagrams 600 of data types returned by an acronymprocessing service. In one embodiment, ParagraphAcronym 602 includesParagraphID 604, a GUID, Acronym 606, a string of text (string), andExpansions 608, a list of Expansions 610. In one embodiment, ParagraphID604 indicates which paragraph Acronym 606 was identified in, while eachExpansion object of Expansions 608 represents a potential expansion ofAcronym 606. For example, if a section of content including the acronym“DVD” 142 was provided to the acronym processing service, anParagraphAcronym 602 received in response may include an Expansionrepresenting “Digital Video Disc” 144 and an Expansion representing“Digital Versatile Disc” 146.

In one embodiment, Expansion 610 includes Name 612, Description 614, andSourceType 616. Name 612 includes the text of the expansion, e.g.“Digital Video Disc”, while SourceType 616 describes the type ofdocument the expansion was defined in (e.g. “email”, “file”, “calendarentry”, etc.). Expansion 610 also includes Score 618, a floating pointnumber (‘double’), which in one embodiment indicates a confidence in theacronym correctly being mapped to this expansion. RelatedEmails 620 andRelatedFiles 622 are lists of objects that further define where theacronym expansion was found, including but not limited to a citation toor a portion of the email/document where the acronym expansion wasfound. RelatedEmails 620 comprises a list of Email 630 objects, each ofwhich includes an ID 632, a Body 634, a Sender 636, and a Subject 638.RelatedFiles 622 comprises a list of File objects, each of whichincludes Name 642 and UniversalResourcelndicator (URI) 644.RelatedPeople 624 includes a list of Person 650 objects, each of whichincludes a Name 652 and an EmailAddress 654 indicating an author of adocument that defines the Expansion. RelatedExpansion 626 includes alist of RelatedAcronym objects, each of which refers to anotherExpansion 610 object of same acronym.

FIG. 7 shows diagrams 700 of data types used to store acronyms,expansions, and the sections of content they are associated with. In oneembodiment, AcronymDataStore 702 includes Acronyms 704, a map ofacronyms to AcronymExpansions objects, and ParagraphToAcronymsMap 706, amap of ParagraphIDs to a list of acronyms.

AcronymDataStore 702 also includes an InsertParagraphAcronyms 708 methodwhich takes a ParagraphID and a list of ParagraphAcronym objects asparameters. The implementation of this function is described below inconjunction with FIG. 8. AcronymDataStore 702 also includes aModifyParagraphAcronyms 710 method which also takes a ParagraphID and alist of ParagraphAcronyms as parameters, and which is described below inconjunction with FIG. 10. AcronymDataStore 702 also includes aRemoveParagraphAcronyms 712 method takes a ParagraphID as the soleparameter, and which is described below in conjunction with FIG. 9.

Acronyms 704 contains a map of Acronyms (e.g. “EDC”) toAcronymExpansions 714 objects. In one embodiment, AcronymExpansions 714objects contain Acronym 716, a string (e.g. “EDC”), Expansions 718, amap of expansions to ExpansionWrapper objects, and SourceParagraphs 720,a map of ParagraphIDs to lists of expansions. In one embodiment,SourceParagraphs 720 tracks which paragraphs contain which expansions ofacronym 716. At the same time, Expansions 718 enables looking up anExpansionWrapper object given the text of an expansion (e.g. “EuropeanDevelopment Center”).

In one embodiment, ExpansionWrapper 722 includes expansion 724, areference to an Expansion 610 object discussed above in conjunction withFIG. 6, and a SourceParagraphs 724 set, which indicates which sectionsof content Expansion 724 is associated with (i.e. which sections containan acronym having the expansion represented by Expansion 724).

FIG. 8 is a flow diagram showing aspects of a routine 800 for updating atask pane displaying acronyms in response to a newly added section ofcontent. Routine 800 may be implemented by the InsertParagraphAcronymsfunction 708 of AcronymDataStore 702.

Routine 800 begins at operation 801, where a list of one or moreParagraphAcronym objects associated with a newly added section ofcontent are received. In one embodiment, a ParagraphID associated withthe newly added section of content is also received.

At operation 803, each acronym in the received list of ParagraphAcronymsis iterated over. In one embodiment, multiple ParagraphAcronyms arereceived from an acronym processing service when a section of contentcontains multiple acronyms, or when multiple sections of content containacronyms.

At operation 805, a determination is made whether an acronym exists inthe Acronyms map 704. In one embodiment, Acronyms map 704 includes aHashMap, and determining whether the acronym exists in the HashMapincludes determining if the HashMap includes the acronym as a key. Ifthe acronym does not exist in the Acronyms map 704, the routine proceedsto operation 807, where an AcronymExpansions object is generated fromthe ParagraphAcronym, and a (Acronym, AcronymExpansions object) pair isadded to the Acronyms map 704.

At operation 809, each expansion of each ParagraphAcronym is iteratedover. In one embodiment, ParagraphAcornym 602 includes a list ofExpansions 608, and so iterating each expansion includes iterating overeach list of Expansions 608 for each received ParagraphAcronym 602.

At operation 811, a determination is made whether an expansion alreadyexists for this acronym in the data store. In one embodiment, thisdetermination is made by querying Acronyms 704 of AcronymDataStore 702for all AcronymExpansion objects 714 associated the acronym. OnceAcronymExpansion objects 714 are identified, the Expansions 718 map ofeach is queried to determine if an ExpansionWrapper 722 for theexpansion in question already exists. If a correspondingExpansionWrapper 722 does not exist, the routine proceeds to operation811, where a new ExpansionWrapper is created and inserted into theExpansions map 718.

At operation 815, a ParagraphID is added to the SourceParagraphs objectsof each AcronymExpansion object and each ExpansionWrapper objectinserted during operations 807 and 813. At the same time, when anAcronymExpansion or an ExpansionWrapper object would have been inserted,but the object already existed (because this acronym and/or expansionwas already associated with a section of content), the ParagraphID isadded to the SourceParagraphs mapping 720 of these “would have beenadded” AcronymExpansion objects and the SourceParagraphs set 724 ofthese “would have been added” ExpansionWrapper objects 722. In this way,operation 815 enables tracking which sections of content contain whichexpansions of which acronyms.

At operation 817, an entry into the ParagraphToAcronymsMap 706 is addedfor the section of content and the acronym name received from theacronym processing service. In this way, AcronymDataStore 702 may useAcronyms map 704 to list all acronyms and expansions identified in thedocument, while ParagraphToAcronymsMap 706 represents which acronymsappear in which sections of content in the document.

At operation 819, acronym display pane 140 is updated based on changesto the acronyms map 704.

FIG. 9 is a flow diagram showing aspects of a routine 900 for updating atask pane displaying acronyms in response to a deleted section ofcontent. Routine 900 may be implemented, in one embodiment, by theRemoveParagraphAcronyns function 712 of AcronymDataStore 702.

Flow diagram 900 begins at operation 901, where in one embodimentParagraphToAcronymsMap 706 is utilized to determine a list of acronymsassociated with the deleted section of content.

At operation 903, for each acronym associated with the deleted sectionof content, as determined in operation 901, one or more AcronymExpansionobjects 714 are determined.

At operation 907, for each of the one or more AcronymExpansion objects714 determined in operation 903, one or more ExpansionWrapper objects722 are determined. In one embodiment, the SourceParagraphs map 720 isused to identify a list of expansions associated with the deletedsection of content. Then, Expansions map 718 is used to map theidentified expansions to associated ExpansionWrapper objects 722.

At operation 909, the ParagraphID of the deleted section of content isremoved from the SourceParagraphs set 724 of each determinedExpansionWrapper object 722.

At operation 911 a determination is made whether a SourceParagraphs set724 is empty after removing the ParagraphID of the deleted section ofcontent. If not, meaning there are other sections of content thatcontain an acronym having this expansion, routine 900 proceeds to areturn block 913.

However, if a sourceParagraphs set 724 becomes empty after removing theParagraphID of the section of content, the routine proceeds to operation915, where the ExpansionWrapper object 722 that contains theSourceParagraphs set 724 is removed from the parent AcronymExpansions714's Expansions map 718. This removal indicates that all sections ofcontent containing acronyms having this expansion have been removed fromthe document.

At operation 917, a determination is made whether, as a result ofremoving the ExpansionWrapper object 722 from the Expansions map 718,the Expansions map 718 is now empty, indicating that this acronym is nolonger contained in any section of content. If it's not, meaning thereare sections of content that contain this acronym, routine 900 proceedsto return block 913.

However, if the Expansions map 718 is empty, the routine proceeds tooperation 919, where the acronym is removed from the AcronymDataStore702's Acronyms map 704 and ParagraphToAcronymsMap 706, signifying thatall instances of the acronym have been removed from the document.

FIG. 10 is a flow diagram showing aspects of a routine 1000 for updatinga task pane displaying acronyms based on a recently updated section ofcontent.

Flow diagram 1000 begins at operation 1001, where a list of one or moreParagraphAcronym objects associated with a modified section of contentare received. As discussed above in conjunction with FIG. 6,ParagraphAcronyms may be received from an acronym processing service.

At operation 1003, expansions indicated in the ParagraphAcronyms objectare inserted into AcronymDataStore 702 as described above in routine800. These expansions represent acronyms still contained within themodified section of content (i.e. after the modification has occurred).In addition to the operations performed in routine 800, all newly addedExpansionWrapper objects are tagged. Already-present ExpansionWrapperobjects encountered while processing routine 800 are also tagged. In oneembodiment tagging an ExpansionWrapper object includes adding areference to the ExpansionWrapper object to a list of visitedExpansionWrapper objects.

At operation 1005, all ExpansionWrapper objects associated with themodified section of content are revisited. In one embodiment,AcronymDataStore revisits these ExpansionWrapper objects as describedabove in conjunction with operations 901-907 of FIG. 9.

At operation 1007, the AcronymDataStore is queried to retrieve alluntagged ExtensionWrapper objects 722, which are removed as discussedabove in conjunction with FIG. 9. Specifically, each untaggedExpansionWrapper is processed as ExpansionWrappers were processed byoperations 909-919.

FIG. 11 shows additional details of an example computer architecture1100 for a computer, such as the computing device 102 (FIG. 1), capableof executing the program components described herein. Thus, the computerarchitecture 1100 illustrated in FIG. 11 illustrates an architecture fora server computer, a mobile phone, a PDA, a smart phone, a desktopcomputer, a netbook computer, a tablet computer, and/or a laptopcomputer. The computer architecture 1100 may be utilized to execute anyaspects of the software components presented herein.

The computer architecture 1100 illustrated in FIG. 11 includes a centralprocessing unit 1102 (“CPU”), a system memory 1104, including a randomaccess memory 1106 (“RAM”) and a read-only memory (“ROM”) 1108, and asystem bus 1110 that couples the memory 1104 to the CPU 1102. A basicinput/output system containing the basic routines that help to transferinformation between elements within the computer architecture 1100, suchas during startup, is stored in the ROM 1108. The computer architecture1100 further includes a mass storage device 1112 for storing anoperating system 1107, other data, and one or more application program100.

The mass storage device 1112 is connected to the CPU 1102 through a massstorage controller (not shown) connected to the bus 1110. The massstorage device 1112 and its associated computer-readable media providenon-volatile storage for the computer architecture 1100. Although thedescription of computer-readable media contained herein refers to a massstorage device, such as a solid state drive, a hard disk or CD-ROMdrive, it should be appreciated by those skilled in the art thatcomputer-readable media can be any available computer storage media orcommunication media that can be accessed by the computer architecture1100.

Communication media includes computer readable instructions, datastructures, program modules, or other data in a modulated data signalsuch as a carrier wave or other transport mechanism and includes anydelivery media. The term “modulated data signal” means a signal that hasone or more of its characteristics changed or set in a manner so as toencode information in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, RF,infrared and other wireless media. Combinations of the any of the aboveshould also be included within the scope of computer-readable media.

By way of example, and not limitation, computer storage media mayinclude volatile and non-volatile, removable and non-removable mediaimplemented in any method or technology for storage of information suchas computer-readable instructions, data structures, program modules orother data. For example, computer media includes, but is not limited to,RAM, ROM, EPROM, EEPROM, flash memory or other solid-state memorytechnology, CD-ROM, digital versatile disks (“DVD”), HD-DVD, BLU-RAY, orother optical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other medium which canbe used to store the desired information and which can be accessed bythe computer architecture 1100. For purposes of the claims, the phrase“computer storage medium,” “computer-readable storage medium” andvariations thereof, does not include waves, signals, and/or othertransitory and/or intangible communication media, per se.

According to various configurations, the computer architecture 1100 mayoperate in a networked environment using logical connections to remotecomputers through the network 1156 and/or another network (not shown).The computer architecture 1100 may connect to the network 1156 through anetwork interface unit 1114 connected to the bus 1110. It should beappreciated that the network interface unit 1114 also may be utilized toconnect to other types of networks and remote computer systems. Thecomputer architecture 1100 also may include an input/output controller1116 for receiving and processing input from a number of other devices,including a keyboard, mouse, or electronic stylus (not shown in FIG.11). Similarly, the input/output controller 1116 may provide output to adisplay screen, a printer, or other type of output device (also notshown in FIG. 11).

It should be appreciated that the software components described hereinmay, when loaded into the CPU 1102 and executed, transform the CPU 1102and the overall computer architecture 1100 from a general-purposecomputing system into a special-purpose computing system customized tofacilitate the functionality presented herein. The CPU 1102 may beconstructed from any number of transistors or other discrete circuitelements, which may individually or collectively assume any number ofstates. More specifically, the CPU 1102 may operate as a finite-statemachine, in response to executable instructions contained within thesoftware modules disclosed herein. These computer-executableinstructions may transform the CPU 1102 by specifying how the CPU 1102transitions between states, thereby transforming the transistors orother discrete hardware elements constituting the CPU 1102.

Encoding the software modules presented herein also may transform thephysical structure of the computer-readable media presented herein. Thespecific transformation of physical structure may depend on variousfactors, in different implementations of this description. Examples ofsuch factors may include, but are not limited to, the technology used toimplement the computer-readable media, whether the computer-readablemedia is characterized as primary or secondary storage, and the like.For example, if the computer-readable media is implemented assemiconductor-based memory, the software disclosed herein may be encodedon the computer-readable media by transforming the physical state of thesemiconductor memory. For example, the software may transform the stateof transistors, capacitors, or other discrete circuit elementsconstituting the semiconductor memory. The software also may transformthe physical state of such components in order to store data thereupon.

As another example, the computer-readable media disclosed herein may beimplemented using magnetic or optical technology. In suchimplementations, the software presented herein may transform thephysical state of magnetic or optical media, when the software isencoded therein. These transformations may include altering the magneticcharacteristics of particular locations within given magnetic media.These transformations also may include altering the physical features orcharacteristics of particular locations within given optical media, tochange the optical characteristics of those locations. Othertransformations of physical media are possible without departing fromthe scope and spirit of the present description, with the foregoingexamples provided only to facilitate this discussion.

In light of the above, it should be appreciated that many types ofphysical transformations take place in the computer architecture 1100 inorder to store and execute the software components presented herein. Italso should be appreciated that the computer architecture 1100 mayinclude other types of computing devices, including hand-held computers,embedded computer systems, personal digital assistants, and other typesof computing devices known to those skilled in the art. It is alsocontemplated that the computer architecture 1100 may not include all ofthe components shown in FIG. 11, may include other components that arenot explicitly shown in FIG. 11, or may utilize an architecturecompletely different than that shown in FIG. 11

The disclosure presented herein also encompasses the subject matter setforth in the following examples.

Example A

A method for updating a first collection and a second collection of adata store associating identifiers and related data, the methodcomprising: receiving an identifier extracted from a modified section ofa document; receiving a piece of data related to the identifier from aremote data store; associating, in the first collection, the identifierwith the modified section of the document; associating, in the secondcollection, the identifier and the piece of related data with themodified section of the document; tagging the piece of related data asexisting in the modified section; querying the first collection and thesecond collection to determine an untagged piece of related dataassociated with the modified section and to determine when the untaggedpiece of related data is not associated with other sections of thedocument; in response to determining when the untagged piece of relateddata is not associated with other sections of the document, removing theuntagged piece of related data from the second collection, wherein theuntagged piece of related data is associated with an additionalidentifier; querying the second collection to determine when theadditional identifier is not associated with any other pieces of relateddata; in response to determining when the additional identifier is notassociated with any other pieces of related data, removing theadditional identifier from the first collection and the secondcollection; updating an identifier pane based on updates to the secondcollection.

Example B

The method of example A, further including: associating a context datawith the piece of related data indicating where in a collection ofdocuments the piece of related data was defined.

Example C

The method of example B, wherein the context data indicates a type ofdocument where the piece of related data was defined.

Example D

The method of example B, wherein the context data indicates an author ofthe document in which the piece of related data was defined.

Example E

The method of example B, wherein the context data includes a portion ofthe document the piece of related data was defined in.

Example F

The method of example E, further comprising: displaying, in theidentifier pane, an indication of a type of document in which the pieceof related data was defined; and in response to a user activation of thecontext data, displaying a portion of the document in which the piece ofrelated data was defined.

Example G

A method for updating a first collection and a second collection of adata store associating identifiers and related pieces of data, themethod comprising: receiving an identifier extracted from a new sectionof a document; receiving a piece of data related to the identifier froma remote data store; associating, in the first collection, theidentifier with the new section of the document; associating, in thesecond collection, the identifier and the related piece of data with thenew section of the document; and updating an identifier pane based onupdated second collection.

Example H

The computing device of example G, wherein the identifier is extractedfrom an updated section of the document.

Example I

The computing device of example G, wherein identifiers in the

identifier pane are sorted based on an alphabetical order or a frequencyof occurrence of the identifier.

Example J

The computing device of example G, wherein identifiers in the identifierpane are prioritized based on which identifiers are visible in anauthoring pane.

Example K

The computing device of example G, wherein the identifier includes anacronym and the related piece of data includes an expansion, wherein thefirst collection includes a paragraph-to-list of acronyms map, andwherein the second collection includes an acronym-to-acronym expansionsobject map.

Example L

The computing device of example K, wherein an acronym expansions objectincludes an acronym, an expansion key-to-expansion object map and asource paragraph-to-list of expansions map, wherein a key of theexpansion key-to-expansion object map includes an expansion string, andwherein an expansion object includes context data and a set ofparagraphs the expansion occurs in.

Example M

The computing device of example L, wherein associating, in the secondcollection, the acronym and the expansion with the new section of thedocument, includes: inserting a section of document ID and a list ofacronyms extracted from the new section of the document into theparagraph-to-list of acronyms map; when an acronym expansions objectdoes not exist for the received acronym and the received expansion,generating an acronym expansions object and inserting it into theacronyms-to-acronym expansions map; when the acronym expansions objectdoes exist for the received acronym and the received expansion, updatingthe acronym expansion object to include the new section of the documentand inserting it into the acronyms-to-acronym expansions map.

Example N

The computing device of example G, wherein the section of the documentincludes a word, a phrase, a sentence, a paragraph, a column, or a page.

Example O

A method for updating a first collection and a second collection of adata store associating identifiers and related pieces of data, themethod comprising: detecting a deletion of a section of a document;identifying an identifier in the deleted section of the document;querying the first collection and the second collection to determinewhen a related piece of data associated with the identifier is notassociated with instances of the identifier in other sections of thedocument; in response to determining when the related piece of data isnot associated with instances of the identifier in other sections of thedocument, removing the related piece of data from the second collection;querying the data store to determine when the identifier is notassociated with any other related pieces of data; in response todetermining when the identifier is not associated with any other relatedpieces of data, removing the identifier from the first collection andthe second collection; updating an identifier pane based on removalsfrom the second collection.

Example P

The method of example O, wherein the method is performed in response todetecting an update to the section of the document.

Example Q

The method of example O, wherein the identifier includes an acronym andthe related piece of data includes an expansion.

Example R

The method of example O, wherein the data store determines when therelated piece of data associated with the identifier is not associatedwith instances of the identifier in other sections of content of thedocument based on a set of section of content identifiers associatedwith the related piece of data being empty.

Example S

The method of example O, wherein the data store determines when theidentifier is not associated with any other related pieces of data basedon an identifiers to related pieces of data map being empty for theidentifier.

Example T

The method of example O, wherein removing the identifier from the datastore includes removing a corresponding entry from an identifiers torelated pieces of data mapping and removing a corresponding entry from asections of the document to identifiers mapping.

Example AA

A method for updating a data store associating acronyms and expansionsextracted from a document being edited and displayed in an authoringpane of an application, wherein the application concurrently displays anacronym pane displaying the acronyms and one or more associatedexpansions, the method comprising: detecting a modification of anexisting section of content of the document; receiving a first acronymextracted from the new section of content; receiving an associatedexpansion of the first acronym from a remote data store; associating thefirst acronym with the section of content in the data store; associatingthe expansion with the section of content into the data store; taggingthe expansion as existing after the modification; querying the datastore to determine an untagged expansion of a second acronym associatedwith the deleted paragraph; querying the data store to determine whenthe untagged expansion is not associated with instances of the secondacronym in other sections of the document; in response to determiningwhen the untagged expansion is not associated with instances of thesecond acronym in other sections of the document, removing the untaggedexpansion from the data store; query the data store to determine whenthe second acronym is not associated with any other expansions; inresponse to determining when the second acronym is not associated withany other expansions, removing the second acronym from the data store;updating the acronym pane based on updates to the data store.

Example AB

The method of example AA, further including: associating a context datawith the expansion indicating where in a collection of documents theexpansion was defined.

Example AC

The method of Example AB, wherein the context data indicates a type ofdocument where the expansion was defined.

Example AD

The method of Example AB, wherein the context data indicates an authorof the document in which the expansion was defined.

Example AE

The method of Example AB, wherein the context data includes a portion ofthe document the expansion was defined in.

Example AF

The method of Example AE, further comprising: displaying, in the acronympane, an indication of a type of document in which the expansion wasdefined; and in response to a user activation of the context data,displaying a portion of the document in which the expansion was defined.

Example AG

A method for updating a data store associating acronyms and expansionsextracted from a document being edited and displayed in an authoringpane of an application, wherein the application concurrently displays anacronym pane displaying the acronyms and one or more associatedexpansions, the method comprising: detecting an addition of a newsection of content added to the document; receiving an acronym extractedfrom the new section of content; receiving an associated expansion ofthe acronym from a remote data store; associating the acronym with thesection of content in the data store; associating the expansion with thesection of content into the data store; updating the acronym pane basedon with the updated data store.

Example AH

The computing device of Example AG, wherein acronyms in the acronym paneare sorted in alphabetical order.

Example AI

The computing device of Example AG, wherein acronyms in the acronym paneare sorted based on a frequency of occurrence of the acronym.

Example AJ

The computing device of Example AG, wherein acronyms in the acronym paneare prioritized based on which acronyms are visible in the authoringpane.

Example AK

The computing device of Example AG, wherein the acronym pane displaysacronyms based on a key of an acronym-to-expansions mapping.

Example AL

The computing device of Example AG, wherein the acronym pane displaysexpansions based on an expansionkey-to-expansionobject mapping, whereina key to the expansionkey-to-expansionobject mapping is based on a valueof the acronym-to-expansions mapping.

Example AM

The computing device of claim 7, wherein the acronym-to-expansionsmapping is implemented with a HashMap.

Example AN

The computing device of claim 7, wherein the section of content includesa word, a phrase, a sentence, a paragraph, a column, or a page.

Example AO

A method for updating a data store associating acronyms and expansionsextracted from a document being edited and displayed in an authoringpane of an application, wherein the application concurrently displays anacronym pane displaying the acronyms and one or more associatedexpansions, the method comprising: detecting a deletion of a section ofcontent of the document; identifying an acronym in the deleted sectionof content; querying the data store to determine when an expansionassociated with the acronym is not associated with instances of theacronym in other sections of the document; in response to determiningwhen the expansion is not associated with instances of the acronym inother sections of the document, removing the expansion from the datastore; querying the data store to determine when the acronym is notassociated with any other expansions; in response to determining whenthe acronym is not associated with any other expansions, removing theacronym from the data store; updating the acronym pane based on removalsfrom the data store.

Example AP

The method of Example AO, wherein the acronym pane is updated to removethe expansion or the acronym.

Example AQ

The method of Example AO, wherein the acronym includes a word and theexpansion includes a definition.

Example AR

The method of Example AO, wherein the data store determines when theexpansion associated with the acronym is not associated with instancesof the acronym in other sections of the document based on a set ofsection of content identifiers associated with the expansion beingempty.

Example AS

The method of Example AO, wherein the data store determines when theacronym is not associated with any other expansions based on an acronymsto expansions map being empty for the acronym.

Example AT

The method of Example AO, wherein removing the acronym from the datastore includes removing a corresponding entry from an acronyms toexpansions mapping and removing a corresponding entry from a paragraphsto acronyms mapping.

Example BA

BA method for updating a list of acronyms and expansions displayed in atask pane in response to a paragraph being added to a live document,wherein the list of acronyms is represented in a data store by aparagraph-acronyms map of paragraphIds to lists of acronym strings andan acronym-to-expansions map of acronym strings to lists ofacronym:expansion objects, wherein each acronym:expansion objectincludes a paragraph-to-expansions map of paragraphIds to lists ofexpansion strings and an expansion key-to-expansion object map ofexpansion strings to expansion objects, wherein expansion objectsinclude expansion context data and an expansion-paragraphs setindicating which paragraphs the expansion has been found in, comprising:receiving an acronym and associated expansion identified within theadded paragraph; adding a paragraphId of the added paragraph and thereceived acronym to the paragraph-to-acronyms map; adding a mappingbetween the acronym and an acronym:expansion pair object to theacronym-to-expansions map; for the added acronym:expansion pair object:adding a mapping between the paragraphId and the expansion to theparagraph-to-expansions map; adding a mapping between the expansion andan expansion object to the expansion key-to-expansion object map; forthe added expansion object, adding the paragraphId to theexpansion-paragraphs set; and updating the task pane with the updatedacronym-expansions map.

Example BB

The method of example BA, wherein the expansion context data includes anindication of where the expansion was defined.

Example BC

The method of example BA, wherein the acronyms and expansions aredisplayed by enumerating the acronym-to-expansions map, wherein each keyof the acronym-to-expansions map, an acronym string, is displayed as anacronym, and wherein each value, a list of acronym:expansion objects, isenumerated to display the expansions.

Example BD

The method of example BA, wherein, when a mapping in the acronyms-to-anacronym:expansion object does not already exist for the receivedacronym, such that the received acronym is not already associated withthe document, generating a new acronym:expansion object and adding anacronym to acronym:expansion object list mapping to theacronym-to-expansions mapping;

Example BE

The method of example BA, wherein, when a mapping in the acronyms-to-anacronym:expansion object already exists for the received acronym, but anacronym:expansion object for does not already exist for the receivedexpansion, adding an acronym:expansion object to the list ofacronym:expansion objects mapped to the received acronym.

Example BF

The method of example BA, wherein the method for updating the list ofacronyms and expansions displayed in the task pane is in response to theparagraph being modified, the method further comprising: tagging eachexpansion object that was generated or would have been generated if itdidn't already exist; traversing each expansion object associated withthe paragraph, and removing untagged expansion objects.

Example BG

A computing device for updating a list of acronyms and expansionsdisplayed in a task pane in response to a paragraph being deleted from alive document, wherein the list of acronyms is represented in a datastore by a paragraph-acronyms map of paragraphIds to lists of acronymstrings and an acronym-to-expansions map of acronym strings to lists ofacronym:expansion objects, wherein each acronym:expansion objectincludes a paragraph-to-expansions map of paragraphIds to lists ofexpansion strings and an expansionkey-to-expansionobject map ofexpansion strings to expansion objects, wherein expansion objectsinclude expansion context data and an expansion-paragraphs setindicating which paragraphs the expansion has been found in, thecomputing device comprising: one or more processors; a memory incommunication with the one or more processors, the memory havingcomputer-readable instructions stored thereupon which, when executed bythe one or more processors, cause the computing device to: determine allacronyms found in the deleted paragraph from the paragraph-to-acronymsmap; determine all acronym:expansion objects associated with thedetermined acronyms from the acronym-to-expansions map; for eachdetermined acronym:expansion object: determine all expansion stringsassociated with the received paragraph from the paragraph-to-expansionsmap, and determine the corresponding expansion objects from theexpansionkey-to-expansionobject map; for each of the determinedexpansion objects: remove a paragraphId associated with the deletedparagraph from the expansion-paragraphs set; when theexpansion-paragraphs set is empty, remove the expansion object from thedetermined expansion object's expansionkey-to-expansionobject map,remove the expansion from the acronym:expansion object'sparagraph-to-expansions map, and remove the correspondingacronym:expansion element from the list of acronym:expansion objectsassociated with the received acronym in the acronym-to-expansions map,as this expansion no longer appears in the document; and updating thetask pane with the updated acronym-expansions map.

Example BH

The computing device of example BG, wherein when the acronym:expansionobject list for the received acronym is empty, remove the acronym fromthe acronym-to-expansions mapping, as the acronym no longer appears inthe document.

Example BI

The computing device of example BG, wherein the expansion context dataincludes an indication that the expansion was defined in one of an emailor a document.

Example BJ

The computing device of example BG, wherein the task pane displays, forone or more of the expansions, a source document type from which theexpansion was defined, based on the context data.

Example BK

The computing device of example BJ, wherein the task pane displays auser interface element associated with the source document type that,when activated by a user, causes the source document to be displayed.

Example BL

The computing device of example BJ, wherein the method for updating thelist of acronyms and expansions displayed in the task pane is inresponse to the paragraph being modified, the method further comprising:inserting acronyms and expansions found in the modified paragraph intothe data store; tagging each expansion object that was, during theinserting, generated or would have been generated if it didn't alreadyexist; and skipping the removal of tagged expansion objects.

Example BM

The computing device of example BG, wherein the task pane is bound tothe acronyms-to-expansions map to display acronyms and their expansions,and wherein the task pane is bound to theexpansionkey-to-expansionobject map to display context informationrelated to the one or more of the expansions.

Example BN

The computing device of example BG, wherein acronyms and expansions areidentified in a paragraph by an acronym processing service.

Example BO

A method for updating a list of acronyms and expansions displayed in atask pane in response to a paragraph being modified in a live document,wherein the list of acronyms is represented in a data store by aparagraph-acronyms map of paragraphIds to lists of acronym strings andan acronym-to-expansions map of acronym strings to lists ofacronym:expansion objects, wherein each acronym:expansion objectincludes a paragraph-to-expansions map of paragraphIds to lists ofexpansion strings and an expansionkey-to-expansionobject map ofexpansion strings to expansion objects, wherein expansion objectsinclude expansion context data and an expansion-paragraphs setindicating which paragraphs the expansion has been found in, comprising:for each of one or more received acronyms and corresponding expansionsidentified within the modified paragraph: adding a paragraphId of theadded paragraph and the received acronym to the paragraph-to-acronymsmap; adding a mapping between the acronym and an acronym:expansion pairobject to the acronym-to-expansions map; for the added acronym:expansionpair object: adding a mapping between the paragraphId and the expansionto the paragraph-to-expansions map; adding a mapping between theexpansion and an expansion object to the expansionkey-to-expansionobjectmap; tagging the added expansion object; when a mapping already existsbetween the expansion and the expansion object in theexpansionkey-to-expansionobject map, tagging the existing expansionobject; for the added expansion object, adding the paragraphId to theexpansion-paragraphs set; for each of the tagged expansion objects:remove a paragraphId associated with the modified paragraph from theexpansion-paragraphs set; when the expansion-paragraphs set is empty,remove the expansion object from the tagged expansion object'sexpansionkey-to-expansionobject map, remove the expansion from theacronym:expansion object's paragraph-to-expansions map, and remove thecorresponding acronym:expansion element from the list ofacronym:expansion objects associated with the received acronym in theacronym-to-expansions map, as this expansion no longer appears in thedocument; and updating the task pane with the updated acronym-expansionsmap.

Example BP

The method of example BO, wherein the expansion context data includes anindication of where the expansion was defined.

Example BQ

The method of example BO, wherein the acronyms and expansions aredisplayed by enumerating the acronym-to-expansions map, wherein each keyof the acronym-to-expansions map, an acronym string, is displayed as anacronym, and wherein each value, a list of acronym:expansion objects, isenumerated to display the expansions.

Example BR

The method of example BO, wherein, when a mapping in the acronyms-to-anacronym:expansion object does not already exist for the receivedacronym, such that the received acronym is not already associated withthe document, generating a new acronym:expansion object and adding anacronym to acronym:expansion object list mapping to theacronym-to-expansions mapping;

Example BS

The method of example BO, wherein, when a mapping in the acronyms-to-anacronym:expansion object already exists for the received acronym, but anacronym:expansion object for does not already exist for the receivedexpansion, adding an acronym:expansion object to the list ofacronym:expansion objects mapped to the received acronym.

Example BT

The method of example BO, wherein the task pane displays a userinterface element associated with the source document type that, whenactivated by a user, causes the source document to be displayed.

1. A method for updating a first collection and a second collection of adata store associating identifiers and related data, the methodcomprising: receiving an identifier extracted from a modified section ofa document; receiving a piece of data related to the identifier from aremote data store; associating, in the first collection, the identifierwith the modified section of the document; associating, in the secondcollection, the identifier and the piece of related data with themodified section of the document; tagging the piece of related data asexisting in the modified section; querying the first collection and thesecond collection to determine an untagged piece of related dataassociated with the modified section and to determine when the untaggedpiece of related data is not associated with other sections of thedocument; in response to determining when the untagged piece of relateddata is not associated with other sections of the document, removing theuntagged piece of related data from the second collection, wherein theuntagged piece of related data is associated with an additionalidentifier; querying the second collection to determine when theadditional identifier is not associated with any other pieces of relateddata; in response to determining when the additional identifier is notassociated with any other pieces of related data, removing theadditional identifier from the first collection and the secondcollection; updating an identifier pane based on updates to the secondcollection.
 2. The method of claim 1, further including: associating acontext data with the piece of related data indicating where in acollection of documents the piece of related data was defined.
 3. Themethod of claim 2, wherein the context data indicates a type of documentwhere the piece of related data was defined.
 4. The method of claim 2,wherein the context data indicates an author of the document in whichthe piece of related data was defined.
 5. The method of claim 2, whereinthe context data includes a portion of the document the piece of relateddata was defined in.
 6. The method of claim 5, further comprising:displaying, in the identifier pane, an indication of a type of documentin which the piece of related data was defined; and in response to auser activation of the context data, displaying a portion of thedocument in which the piece of related data was defined.
 7. A method forupdating a first collection and a second collection of a data storeassociating identifiers and related pieces of data, the methodcomprising: receiving an identifier extracted from a new section of adocument; receiving a piece of data related to the identifier from aremote data store; associating, in the first collection, the identifierwith the new section of the document; associating, in the secondcollection, the identifier and the related piece of data with the newsection of the document; and updating an identifier pane based onupdated second collection.
 8. The computing device of claim 7, whereinthe identifier is extracted from an updated section of the document. 9.The computing device of claim 7, wherein identifiers in the identifierpane are sorted based on an alphabetical order or a frequency ofoccurrence of the identifier.
 10. The computing device of claim 7,wherein identifiers in the identifier pane are prioritized based onwhich identifiers are visible in an authoring pane.
 11. The computingdevice of claim 7, wherein the identifier includes an acronym and therelated piece of data includes an expansion, wherein the firstcollection includes a paragraph-to-list of acronyms map, and wherein thesecond collection includes an acronym-to-acronym expansions object map.12. The computing device of claim 11, wherein an acronym expansionsobject includes an acronym, an expansion key-to-expansion object map anda source paragraph-to-list of expansions map, wherein a key of theexpansion key-to-expansion object map includes an expansion string, andwherein an expansion object includes context data and a set ofparagraphs the expansion occurs in.
 13. The computing device of claim12, wherein associating, in the second collection, the acronym and theexpansion with the new section of the document, includes: inserting asection of document ID and a list of acronyms extracted from the newsection of the document into the paragraph-to-list of acronyms map; whenan acronym expansions object does not exist for the received acronym andthe received expansion, generating an acronym expansions object andinserting it into the acronyms-to-acronym expansions map; when theacronym expansions object does exist for the received acronym and thereceived expansion, updating the acronym expansion object to include thenew section of the document and inserting it into theacronyms-to-acronym expansions map;
 14. The computing device of claim 7,wherein the section of the document includes a word, a phrase, asentence, a paragraph, a column, or a page.
 15. A method for updating afirst collection and a second collection of a data store associatingidentifiers and related pieces of data, the method comprising: detectinga deletion of a section of a document; identifying an identifier in thedeleted section of the document; querying the first collection and thesecond collection to determine when a related piece of data associatedwith the identifier is not associated with instances of the identifierin other sections of the document; in response to determining when therelated piece of data is not associated with instances of the identifierin other sections of the document, removing the related piece of datafrom the second collection; querying the data store to determine whenthe identifier is not associated with any other related pieces of data;in response to determining when the identifier is not associated withany other related pieces of data, removing the identifier from the firstcollection and the second collection; updating an identifier pane basedon removals from the second collection.
 16. The method of claim 15,wherein the method is performed in response to detecting an update tothe section of the document.
 17. The method of claim 15, wherein theidentifier includes an acronym and the related piece of data includes anexpansion.
 18. The method of claim 15, wherein the data store determineswhen the related piece of data associated with the identifier is notassociated with instances of the identifier in other sections of contentof the document based on a set of section of content identifiersassociated with the related piece of data being empty.
 19. The method ofclaim 15, wherein the data store determines when the identifier is notassociated with any other related pieces of data based on an identifiersto related pieces of data map being empty for the identifier.
 20. Themethod of claim 15, wherein removing the identifier from the data storeincludes removing a corresponding entry from an identifiers to relatedpieces of data mapping and removing a corresponding entry from asections of the document to identifiers mapping.